Network Support Library/RoseWare - Network Support Library.iso/mhs/v15b_n.exe/V15B_N.TXT

Text File | 1993-09-17 | 18KB | 454 lines

              NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              REV B Upgrade for MHS V1.5N
DOCUMENT ID:        TID000421
DOCUMENT REVISION:  A
DATE:               01JUL93
ALERT STATUS:       Yellow
INFORMATION TYPE:   Symptom Solution
README FOR:         V15B_N.EXE

NOVELL PRODUCT and VERSION:
NetWare MHS 1.5

ABSTRACT:
The file, V15B_N.EXE, upgrades MHS v1.5n to MHS v1.5n revision B.  The file
fixes the problem of gateways regenerating the Send-To header.  The file
also compares extended addresses for uniqueness, and supports password
encryption.
_________________________________________________________________

DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.
NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.
HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION
ONLY.  NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS
INFORMATION.
_________________________________________________________________

Self-Extracting File Name:  V15B_N.EXE

Files Included     Size     Date        Time

\
  V15B_N.TXT             (This File)
 UPGRADE.EXE      22226   01-07-92     11:44a
     SYS.EXE     315210   09-17-93      1:34a
     EXE.EXE     216437   09-17-93      1:32a


                 RELEASE NOTE

NetWare(R) MHS(tm) Network Edition
----------------------------------

Software v1.5N Revision B
-------------------------

The NetWare MHS Network edition software uses the Standard Message Format
(SMF) to provide DOS-based messaging services on NetWare networks.  NetWare
MHS transfers information containing addresses, text, and other data from
an MHS-compatible application or gateway to applications and gateways at
other locations.  MHS uses a store-and-forward communications method, which
transports messages across a broad range of data-communications networks.
The NetWare MHS Network edition stores messages and forwards them to other
locations or applications.  Other applications provide services - such as
electronic mail - that allow users to create and process messages.

NetWare MHS v1.5 incorporates new features and an improved user interface
for installation and administration, and it uses a revised version of the
Standard Message Format (SMF) for exchanging electronic messages.

If you need connectivity between NetWare MHS and CompuServe, either to use
the CompuServe hub service, or to send mail from MHS to CompuServe
subscribers, obtain the MHS 1.5 upgrade option from CompuServe.  If you
have a CompuServe subscription you can obtain it by signing on to
CompuServe and entering "GO MHS" at the CompuServe Main Menu screen.  For
more information, call CompuServe at 800-848-8199 or 614-457-0802.

Please read this entire release note and Chapter 2 of the NetWare MHS
Installation and Operations Guide before installing the NetWare MHS
software.


If you have any questions or comments, please contact:

    Customer Support Response Center
    Novell, Inc.
    2180 Fortune Drive
    San Jose, CA 95131

If you need information about the Novell mail hub (NHUB) or about
registering your workgroup, call the Messaging Hotline at the following
number:

    [phone]

To register your workgroup, you can send an MHS mail message to
hubadmin@NHUB.    In the message, include your workgroup name, your contact
phone number, and the name of the contact person in your organization.

If you need technical support, call one of the following numbers:

    (800) NETWARE
    [phone]


For other information, send a fax to the attention of the MHS Product
Manager at the following number:

    [phone]


Components
----------

The NetWare v1.5N Rev. B upgrade consists of these components:

o   UPGRADE.EXE, the program you execute to perform the upgrade.

o   EXE.EXE and SYS.EXE, which are invoked by the UPGRADE program (do not
execute them).

o   README.DOC, this release note.


System Requirements
-------------------

NetWare MHS Rev.  B (Network edition) requires the following hardware and
software:

o   NetWare MHS v1.5N Rev. A

o   Minimum of 200 free directory entries

NetWare MHS v1.5 Rev.  B has the same hardware requirements as NetWare MHS
v1.5 Rev.  A.


*****************************************************************
*            Warning                     *
*                                *
*A small number of third-party utility programs change internal *
*MHS configuration information and queue headers contained in   *
*NETMGR.QUE.  NetWare MHS does not support these changes; they  *
*will cause an unrecoverable error when you run NetWare MHS v1.5*
*Rev.  B.  Contact the manufacturer of your MHS utility, to find*
*out if your utility is supported.  If it is not, please remove *
*it from your system before you upgrade to NetWare MHS v1.5 Rev.*
*B.                                *
*****************************************************************


NetWare MHS v1.5 Rev. B Compatibility
-------------------------------------

NetWare MHS v1.5 Rev.  B is fully compatible with NetWare v1.5 Rev.  A,
v1.5C, and v1.1.  It is not compatible with third-party MHS utilities that
make unsupported changes to NETMGR.QUE.


Upgrading from NetWare MHS V1.5
-------------------------------

To upgrade your current version of NetWare MHS to NetWare MHS v1.5N Rev. B,
follow these steps:

1.  Make sure that MHS has delivered all pending mail.

2.  At the MHS host, halt all gateways, MHS applications, and the
Connectivity Manager, if they are currently running. To halt the
Connectivity Manager, press <Esc>.

3.  Back up the existing SYS, MAIL and EXE subdirectories.

4.  Log in as Supervisor or Supervisor equivalent on the NetWare server on
which MHS is installed.

5.  Set the MV environment parameter to point to the path containing the
MHS subdirectory. For example, if NetWare MHS is installed in
SERVER1/SYS:MAIL, enter the command "SET MV=SERVER1/SYS:MAIL".

6.  Change to the directory containing the UPGRADE.EXE program, and run the
Upgrade program by typing:

    UPGRADE <Enter>

    The Upgrade program prompts, 'Would you like to view the README file
(Y/N)?'

7.  To display the README file, type "Y". If you have already read the
README file, type "N".

The Upgrade program prompts, 'Confirm that the path to the MHS files is the
one you wish to upgrade (path). Is it OK to continue (Y/N)?'

8.  Type "Y" if the path displayed in the prompt is the path containing the
MHS files and programs. The Upgrade program upgrades your NetWare MHS
installation to Revision B.

Type "N" if the path is incorrect.  The Upgrade program terminates.
Set the MV environment parameter, and begin again at step 6.


Documentation Corrections
-------------------------

This section provides updates and corrections to the NetWare MHS
Installation and Operation Guide.


Passwords for Asynchronously-Connected Hosts
--------------------------------------------

The NetWare Installation and Operation Guide incorrectly describes how to
define passwords for hosts with which you communicate asynchronously.

You can define a Password for access to hubs in the MHS HOST SETUP form.
This is the password that the local host transmits when it communicates
with a remote host.  (It transmits the same password to all the remote
hosts with which it communicates.)

For each remote host the local host calls, and for each remote host that
calls the local host, you can define a Password (in the "A HOST THAT THIS
HOST PHONES" and the "A HOST THAT PHONES THIS HOST" forms,
respectively).    This Password must match the password defined in the
Password for access to hubs field in the remote host's HOST SETUP form.

If you do not define the remote host's password at your local host, MHS
will take the password transmitted by the remote host in the next
communication session, and write it in the Password field.

Once a password has been assigned to a remote host, the remote host
administrator must notify you of changes to the password.  When the remote
administrator changes the password in the Password for access to hubs
field, the local administrator must change the Password field in the "A
HOST THAT THIS HOST PHONES" or the "A HOST THAT PHONES THIS HOST" form for
the remote host.  Otherwise, if Require Password is set to "Yes," a
password mismatch will occur, and the hosts will be unable to establish a
communication session.

Similarly, when you change the password in the Password for access to hubs
field, you must ask the administrator of the remote host to update the
Password in the form for your host.

To understand how passwords work, consider "Eng," a host that calls another
host named "Sales." Sales has chosen "salpas" as its Password for access to
hubs, and Eng has chosen "engpas" as its Password for access to hubs.
These passwords are defined in the HOST SETUP form.

The administrators at Sales and Eng can get together and coordinate
passwords.  Sales' administrator enters "engpas" in the Password field of
the "A HOST THAT THIS HOST PHONES" form that defines the route to Eng.  And
Eng's administrator enters "salpas" in the Password field of the "A HOST
THAT PHONES THIS HOST" form that defines the route to Sales. Both
administrators can also set Require Password to Yes.


One or both administrators can choose not to define the password for the
other host.  If they leave the Password for the remote host blank, MHS will
insert the password it receives during the next communication session.
During this session, Eng's MHS transmits its password.  Sales' MHS enters
the password received from Eng in its routing table, and send its password
to Eng's MHS.  Eng's MHS enters the Sales password in its routing table,
and continues the transmission.

From now on, if either administrator changes its Password for access to
hubs, they must ask the other administrator to change the Password field in
the "A HOST THAT THIS HOST PHONES" or "A HOST THAT PHONES THIS HOST" form
for the remote host.


96V32 and 96V32HUB Modem Driver
-------------------------------

The 96V32 and 96V32HUB are not drivers for the Hayes Smartmodem, as stated
in the NetWare MHS Installation and Operation Guide. They are drivers for
the Hayes V-series ULTRA modem.


Features of NetWare MHS v1.5 Rev. B
-----------------------------------

NetWare MHS v1.5N Rev.    B incorporates the following new and revised
features:

o   Improved Monochrome Support. Several new command-line switches have
been added for use with monochrome monitors.  They are the following:

-M  Disables color on IBM PS/2s and monochrome VGA displays.

-R  Displays the currently selected item in reverse video on laptops that
do not display bold text.

-U  Displays the currently selected item as underlined text on laptops that
do not display bold text.

The -M, -R and -U switches are mutually exclusive.  To display selected
attributes in reverse video, use the command MHS -R.

o   Faster "Copy a List" Processing. The "Copy a list to a file" process is
faster.

o   Recovery Counter Reset. The Abort/Retry counter is reset after a
successful connection.

o   Retry Counter Reset.  The Retry Counter resets after a successful
connection to another host.

o   Support for Modems That Use One Stop Bit. To support new modems with
software UARTs that use only one stop bit for communication, NetWare MHS
uses only one stop bit. It also supports modem definitions with large
command sets.

o   Support for Additional Modem Drivers. In addition to the modem drivers
listed in Appendix C of the NetWare MHS Installation and Operation Guide,
NetWare MHS now supports the following modem drivers.

2400B     For Hayes Smartmodem 2400 and Hayes-compatible modems operating at
2400 baud.  Use for calling hosts.
2400B     For Hayes Smartmodem 2400 and Hayes-compatible modems operating at
2400 baud.  Use for both hubs and calling hosts.
96V32     For Hayes V-Series ULTRA 9600 modems.    Use for calling hosts.
96V32HUB For Hayes V-Series ULTRA 9600 modems.    Use for both hubs and
calling hosts.
BULLET96 For E-Tech BulletModem E9696M modems without MNP.
BULLETEC For E-Tech BulletModem E9696M modems with MNP.
DISABLED To disable asynchronous activity.  For hosts that do not exchange
messages with remote hosts through telephone calls.
FAXMDM     For generic SendFax-compatible modems.
HAYESMAN For Hayes-compatible modems that require telephone numbers to be
dialed manually.
HAYES-UN For Hayes-compatible modems operating at speeds up to 2400 baud.
Use for both hubs and calling hosts.
HAYESX24 For generic Hayes-compatible 2400 baud modems.
HAYESSM     For Hayes Smartmodem 2400 modems.
HSTD-HUB For US Robotics COURIER HST modems with MNP. Use for both hubs and
calling hosts.
HSTDNMNP For US Robotics COURIER HST modems without MNP.
INTELFAX For the Intel SatisFAXtion board.
INTELV32 For Intel 9600EX modems.
MICROCOM For Microcom QX4232HS modems.
NULLMDM     For hosts with a direct cable connection between their
communication ports.  You can use NULLMDM as a platform for developing
modem-control files.
PP96-HUB For Practical Peripherals PM9600SA modems. Use for both hubs and
calling hosts.

This list supersedes the one in Appendix C of the NetWare MHS Installation
and Operation Guide.

Note: If you want to use one of these modem drivers, refer to the MODEM.DOC
file in the SYS directory for installation instructions.

o   SMFUTIL.DOC Updated. The online documentation for SMFSEND is more
thorough.

o   SEND-TO Support. When an SMF version 70 gateway delivers a message to
MHS, MHS will not regenerate the SEND-TO field if a valid SEND-TO field
exists.

o   Support for Extended Addresses. While MHS v1.5 Rev. B does not use
extended address to route messages, it now examines extended address
elements in braces ({ }) when checking for duplicate addresses.

For example, a message contains the following addresses:

    mail@fax {FAX: [phone]}
    mail@fax {FAX: [phone]}

Previously, MHS would compare only the base address (mail@fax).  Since the
base address is the same in both instances, MHS v1.5 would only deliver one
message, containing the first address, to the fax gateway.  MHS 1.5 Rev.  B
recognizes the two addresses as distinct, and delivers two copies to the
fax gateway.  Note that MHS does not interpret the contents of the braces;
it only knows they are different.    Thus, if in the above example, the
addresses were:

    mail@fax {FAX: [phone]}
    mail@fax {FAX: [phone]}

    then MHS would send two copies.

This change supersedes the information in the SMF Programmer's Reference.


o   Support for NetWare 386 Encrypted Passwords.  NetWare MHS supports
password encryption on 386 file servers.  If you turned off password
encryption in your AUTOEXEC.NCF file when you installed a previous version
of NetWare MHS, you now have the option to turn it back on.


General Restrictions
--------------------

The following general restrictions apply to networks running NetWare MHS
v1.5:

o   Monochrome Monitor Problems. The MHS screens may be difficult or
impossible to read on certain VGA monochrome monitors.  If you experience
this problem, use the following MODE command at the DOS prompt before
running MHS:

    MODE=bw80

o   Color Monitor Problems. If the colors on an application display
incorrectly after you run MHS, use the following MODE command at the DOS
prompt before running your application:

    MODE=co80

o   Default Primary Host. In new installations, the default primary host
for non-routing internet hosts is NHUB.  If you do not change this, no mail
will be delivered to or routed from the non-routing host.

o   Continuous Internet Retries.  Under some circumstances, the
Connectivity Manager may appear to have stopped working.  This occurs
because it may retry 25 times after waiting for the IPX-retry interval for
your NetWare installation (20 seconds by default) for each retry.  At the
maximum, the Connectivity Manager waits continuously for 8 minutes and 20
seconds if it has continual and successive retries.  After this period, MHS
recovers and restarts the Connectivity Manager.

o   Inaccurate Estimated Transfer Time. MHS attempts to estimate the amount
of time an asynchronous transfer will take.    It often estimates incorrectly,
especially for high-speed modems.

o   Memory Allocation Error.  If the NetWare MHS workstation has a limited
amount of available memory, and a large number of files accumulate in the
SND directory, a memory allocation error will occur.  Delete any *.BAD
files in the SND directory and, if possible, terminate memory-resident
programs sharing the MHS workstation.  Do not run MHS from a shell.

o   The MAIL Variable. While it is possible in the Network Edition to
specify the MV variable for one drive and the MAIL for another, both must
be mapped network drives.  You cannot specify any local drives.  Appendix A
of the MHS 1.5 Installation and Operations Guide incorrectly implies that
you can use a local drive.

o   Gateway Version Number.  MHS sometimes sets the default version number
of a gateway to 61.    Please ensure you set the version number to either 64
or 70.  Read your gateway's documentation or call your gateway supplier if
you do not know which version number to use.


Trademarks
----------

Novell, the N design,  and NetWare are registered trademarks and NetWare
MHS is a trademark of Novell, Inc.

CompuServe is a registered trademark of CompuServe, Inc.  Da Vinci Systems
is a registered trademark of Da Vinci Systems Corp.  E9696M and BulletModem
are trademarks of E-Tech, Inc.  Hayes and V-series are registered
trademarks and ULTRA and Smartmodem are trademarks of Hayes Microcomputer
Products, Inc.  Intel is a registered trademark and SatisFAXtion is a
trademark of Intel Corporation.  Microcom and MNP are registered trademarks
of Microcom, Inc.  Practical Peripherals is a registered trademark and
PM9600SA is a trademark of Practical Peripherals, Inc.  USRobotics is a
registered trademark and COURIER, HST, and ASL are trademarks of U.S.
Robotics, Inc.